T0_Schema_Dictionary [ACTIVE v1.3].md

canon/tiers/00_Tier_0_Master_Indices/T0_Schema_Dictionary [ACTIVE v1.3].md

T0\_Schema\_Dictionary

Humanity Project Tier 0 Registry Schema Dictionary. Joshua Alexander Milks. CONFIDENTIAL.

This doc carries canonical schema authority for the Tier 0 registry layer of the Humanity project canonical store. Per-registry schema specification, universal column conventions, entity\_id format roster, schema version pin policy, and populated\_from field-granular source-tracking discipline lock here. Thirty T0 registries hold canonical schema documentation at Phase 5M-5 Phase F lock scope: twenty-two at active populate state per §3, six at scope-locked state per §4, two at newly spun state per §5. Five 5M-2 spawned-by-pipeline registries promote from §6 forward references at 5M-1 lock to §3 active populate sections §3.17 through §3.21 at this v1.1 lock per pipeline contract §X.5 and §X.6 full schema absorption.

§1 Document Purpose and Authority

T0\_Schema\_Dictionary owns canonical schema documentation for the Tier 0 registry layer. Per-registry column rosters, allowed value enums, foreign-key reference conventions, populate-state status, drive ID resolution, and version pin policy live here. The dictionary is the canonical lookup surface for AI consumers including the Region Builder agent at Project 3 Region Building Flores Island launch, the Spine Cascade agent at Phase 6 spine resume, the Quest Writer agent at Phase 6 standard quest track authoring, and the build-pipeline orchestration agents across §1-§10 of T1\_Build\_Pipeline\_Contracts.

Authority hierarchy. CVD §17 hard lines bind absolute on schema decisions that touch canonical hard line discipline. T1\_Architecture\_and\_State Tier 0 Registry Architecture section owns registry roster scope, populate-state taxonomy, and folder structure resolution. T1\_Build\_Pipeline\_Contracts §X.6 sections own per-pipeline column-add commitments that this dictionary absorbs at registry-level schema documentation. This dictionary owns canonical column-level schema lookup. Where this dictionary conflicts with a pipeline contract §X.6 column-add commitment, the pipeline contract wins for that specific column add and this dictionary updates to absorb the resolution. Where this dictionary conflicts with a T1 reference doc on domain-specific schema authority (T1\_Vril governs vril site schema details, T1\_Combat governs weapon schema details, T1\_Trades governs trade registry schema details), the T1 reference doc wins and this dictionary documents the canonical resolution.

Version pin. This dictionary at ACTIVE v1.3 locks at HUM Pre-Chunk-5A Cleanup Pass Session C Wave 3 per §7 Version History. v1.0 locked at Phase 5M-1 close covering universal conventions plus per-registry schema documentation for 24 in-scope T0 registries plus forward references for 5 pending 5M-2 spawned registries. v1.1 MINOR version bump at Phase 5M-2 close absorbed 5 spawned-by-pipeline T0 registry schema documentation from §6 forward references to §3 active populate sections §3.17 through §3.21 per pipeline contract §X.5 and §X.6 full schema absorption. v1.2 MINOR version bump at Phase 5M-5 Phase F close absorbs T0\_Research\_Corpus\_Registry schema documentation at new §3.22 active populate section per HUM-T1-RCM-V1-COMPLETE May 16 paired registry creation, plus four PATCH-grade drift-fix patch sets bundled into the v1.2 lock per §7 v1.2 entry. Thirty T0 registries hold canonical schema documentation at Phase 5M-5 Phase F lock scope: twenty-two at active populate state per §3, six at scope-locked state per §4, two at newly spun state per §5. Subsequent MAJOR version bumps trigger AI consumer re-pin cascade per §2.3 schema version discipline. Subsequent MINOR version bumps add new registries or new columns without breaking existing consumers. PATCH bumps resolve documentation drift without schema change.

§2 Universal Conventions

Universal columns and conventions apply across all T0 registries per the conventions documented in this section. Per-registry sections in §3 through §6 reference these conventions by pointer rather than re-specifying them per registry.

§2.1 entity\_id format

Every T0 registry carries a primary key column documenting the unique row identifier. The universal format is PREFIX\_NNNN where PREFIX is an uppercase 2-5 character registry-specific token and NNNN is zero-padded digit count appropriate to registry scale. Single underscore separates prefix from numeric. Stable across registry updates. Used as foreign key reference from other T0 registries and from T8 region pages.

Per-registry prefix assignments lock at §2.7 universal entity\_id roster. Pre-existing canonical IDs from prior populate work honor their established formats where canonical lock predates this dictionary; new IDs at Phase 5M and beyond conform to the universal pattern. Where pre-existing canon and new universal pattern conflict, drift surfaces at the per-registry section in §3 through §6 with explicit resolution path.

§2.2 populated\_from format

Every T0 registry row carries a populated\_from column documenting per-field provenance for the row's data. The column carries a JSON-object value mapping field-name string to source-array carrying one or more canonical source citations. Format per cell:

The JSON object structure carries field-name as key and source-array as value. Source-array elements are canonical citation strings covering CVD §N.N format for CVD substrate, T1\_DocName §N.N format for T1 reference doc substrate, T8\_Region\_NNN §N format for T8 region page substrate, primary-source attribution strings for §8 Book Processing extraction stream substrate, and manual\_author\_lock string for fields populated through direct author authoring without external citation. Multi-source-derived cells carry multi-element arrays. Empty arrays per field flag the field as a populate gap surfaced at validation.

Example structure conveying single source for one field plus multi-source-derived for another field plus empty gap for a third field: the JSON object contains three keys covering field\_name\_1 with source array carrying one CVD reference citation, field\_name\_2 with source array carrying both a CVD reference citation and a T1 reference citation for cross-source-derived data, field\_name\_3 with empty source array flagging populate gap.

Validation discipline. Project 3 Region Building Flores Island gating requires per-field populated\_from coverage at non-empty source array per active populate registry row. Empty source array per field equals validation gap surfaced at citation audit per §8.4 of T1\_Build\_Pipeline\_Contracts Book Processing Pipeline Contract.

§2.3 Schema version semantics

Per-registry schema version locks at MAJOR.MINOR.PATCH format per registry. AI consumers pin to specific MAJOR.MINOR.PATCH version at build time. Cross-registry validation queries this dictionary for current per-registry version state.

MAJOR version bump triggers when schema change breaks AI consumer pin. Column removal, column rename, enum value removal, primary key format migration, or foreign-key reference target change qualify as MAJOR bumps. MAJOR bumps trigger cascade across pipeline contract §X.10 Schema Version Discipline halt protocols; AI consumers halt and require migration handling per §1.11 of T1\_Build\_Pipeline\_Contracts.

MINOR version bump triggers when schema change extends without breaking. New optional column addition, new enum value addition within existing column, new foreign-key reference addition, or new validation rule extension qualify as MINOR bumps. AI consumers ignore unknown columns per §1.11 of T1\_Build\_Pipeline\_Contracts; MINOR bumps do not halt builds.

PATCH version bump triggers when documentation patches resolve schema-doc drift without altering canonical schema. Spelling corrections, prose clarifications, drift-fix annotations, and cross-reference repairs qualify as PATCH bumps. AI consumers ignore PATCH bumps transparently.

§2.4 recent\_changes column

Every T0 registry row carries a recent\_changes column documenting per-row change history. The column carries an array of change-event objects in reverse chronological order. Per-event structure covers timestamp at ISO-8601 format, change\_type enum covering create, update, deprecate, restore, version\_bump, and change\_summary text under 200 characters describing the change. Last 10 events retain at row level; earlier history archives via per-registry change log doc at Tier 99 operational scope.

§2.5 cross\_reference\_array

T0 registries carrying foreign-key reference arrays to other T0 registries use the cross\_reference\_array column convention. The column carries an array of foreign-key reference strings in PREFIX\_NNNN format matching the target registry primary key. Multi-target cross-references carry namespace-prefixed strings covering target\_registry\_name colon entity\_id format such as T0\_Vril\_Site\_Registry:VS\_CH15\_001 where namespace disambiguation is canonical authority.

§2.6 last\_updated and version columns

Every T0 registry row carries last\_updated column at ISO-8601 timestamp format documenting the last successful update timestamp. version column at MAJOR.MINOR.PATCH format documents the per-row schema version pin where row-level schema variance exists; registry-level uniform schema carries registry-level version pin only.

§2.7 Universal entity\_id roster

Universal entity\_id prefix assignments per T0 registry lock at this section. Pre-existing canonical formats from prior populate work honor at registry section in §3 through §6 with drift annotation where applicable.

Locked at 5M-1 scope:

Locked at 5M-2 scope per pipeline contract spawn:

Proposed at per-registry populate time. Format locks at registry section in §4 with populate-session author confirmation:

Pre-existing format honored. T0\_Language\_Script\_Registry uses descriptive slug format covering MEROITIC, HIEROGLYPH\_EGYPTIAN, AKKADIAN\_CUNEIFORM, and similar canonical-substrate-descriptive identifiers; LANG\_NNN universal pattern proposed but not locked at 5M-1 to honor pre-existing canonical identifier load.

T0\_Theme\_Registry, T0\_Voice\_Registry, T0\_Scene\_Spec\_Registry, T0\_Quest\_Definition\_Registry primary keys honor pre-existing descriptive snake\_case slug format per T1\_Build\_Pipeline\_Contracts §3.6, §4.6, §5.5, §6.5 canonical-spawn spec at "Unique slug, snake\_case, descriptive" formal specification. Format examples cover PROTAGONIST\_THEME, CASSIUS\_PHASE\_1, GRAND\_SAGE\_REVEAL, ENDING\_TRULY\_GOOD for themes; PROTAGONIST\_VOICE\_BASE, GRAND\_SAGE\_REVEAL\_VOICE, CASSIUS\_PHASE\_1\_VOICE for voices; SCENE\_CH77\_ENDING\_TRULY\_GOOD, SCENE\_CH76\_CASSIUS\_PHASE\_1\_INTRO, SCENE\_PROLOGUE\_OPENING for scenes; QUEST\_CH77\_ENDING\_TRULY\_GOOD, QUEST\_CH76\_CASSIUS\_PHASE\_1, QUEST\_TRADE\_07\_HAITI\_HOME\_BASE for quests. TH\_NNNN, VO\_NNNN, SC\_NNNN, QU\_NNNN universal pattern proposed at Schema Dictionary §2.7 v1.0 lock retains as proposed migration option but does not lock at 5M-2 to honor pre-existing pipeline contract canonical spec. Per-registry populate session at 5M-3 Drive populate carries the descriptive-slug-versus-PREFIX\_NNNN decision with author confirmation parallel to T0\_Language\_Script\_Registry descriptive-slug-versus-LANG\_NNN deferred decision treatment.

T0\_Vril\_Site\_Registry uses VS\_CHXX\_NNN composite-id format per pre-existing canonical lock at §3.5; VS\_NNN universal pattern with separate chapter\_anchor FK column proposal defers to per-registry populate session author decision parallel to other pre-existing-format honoring patterns above.

§2.8 Cross-registry collision avoidance

Universal entity\_id roster lock at §2.7 resolves cross-registry namespace ambiguity. Each PREFIX value is unique per registry; no two registries share a prefix. The chapter-versus-character collision identified at Buildability Audit P0 resolves through CHAR\_ rename for character registry, freeing CH\_ for chapter registry. Universal entity\_id format pattern PREFIX\_NNNN with registry-specific prefix prevents collision at canonical lock.

§2.9 extensions column convention

T0 registries spawned via pipeline contracts at §3.17 through §3.21 carry an extensions column documenting forward-compatibility JSON storage. The column carries a JSON-object value with arbitrary string keys and JSON values. Purpose is to enable schema additions that downstream AI consumers do not yet pin without triggering MAJOR version bump cascade per §2.3 schema version discipline.

Lifecycle. New per-row fields surface in canonical authoring at pipeline contract build time. Where the field is universal across the registry, MINOR version bump per §2.3 adds a typed column and the field migrates from extensions to its typed column on the bump. Where the field is per-row situational and consumers do not benefit from typed access, the field persists in extensions across registry-wide queries.

AI consumer discipline. Consumers reading extensions check for key presence before access. Missing keys do not halt builds per §1.11 of T1\_Build\_Pipeline\_Contracts unknown-column tolerance. Consumers do not pin on extensions key presence; pinned-on schema lives at typed columns only.

Format. JSON object value covers arbitrary string keys mapping to JSON values. Recommended depth limit two levels; deeper nesting surfaces as a candidate for typed column migration at next MINOR bump review.

Authority. T0\_Schema\_Dictionary at this section owns canonical extensions column convention authority. Pre-Phase-5L-Distribution authority resided at Blueprint v4.1 §4.1; Blueprint v4.1 archived at 5L Distribution per T1\_Architecture\_and\_State Tier 0 Registry Architecture section and §3.7 drift-fix paragraph. Schema Dictionary §2.9 v1.3 lock supersedes Blueprint §4.1 reference for extensions column convention. Per-registry sections in §3.17 through §3.21 reference §2.9 for extensions column spec.

§2.10 Deferred-FK encodings: range\_id and the thread two-encoding

Two id columns are DELIBERATELY not foreign keys, documented here so a later reader does not "repair" a non-problem. Authority for this section is docs/fk\_spec.json (the fidelity/FK harness contract); the two are kept aligned.

Grouping label, not a foreign key. The range\_id column (format R\_NN\_NN, e.g. R\_16\_25) on T0\_Chapter\_Index names the ten-chapter Range-Review window a chapter falls in. It is a GROUPING LABEL — there is no Range registry and none is planned (a range is a review cadence, not a canon entity). fk\_spec validates it as an id-format only (pattern plus a not-null floor) and does not declare it under foreign\_keys; it is not a dangling FK.

Thread id, three surface encodings, one canonical thread. The same twenty-two threads appear under three surface encodings, all keyed on the shared two-digit thread number: (1) the CANONICAL key T\\d{2} — T01 through T22 — in T0\_Thread\_Registry, the authority for the roster; (2) the GRID key THREAD\_\\d{2} — THREAD\_01 through THREAD\_22 — in T0\_Thread\_Grid, the per-chapter grid; (3) the PACKED form T\\d{2}:SUFFIX — for example T01:A — in T0\_Chapter\_Index.thread\_anchors\_complete, where SUFFIX is the per-chapter completion status (A, C, E, NP, RF, RP). The harness bridges (3) to (2) as an enforced FK by matching the two-digit number; the mappings to the canonical (1) are the same number and are DOCUMENTED here rather than re-encoded or added as a second enforced FK, because canonicalizing the surfaces would churn the frozen fidelity baseline for no integrity gain. The confirmed-valid companion FK is T0\_Thread\_Grid.chapter\_id to T0\_Chapter\_Index.chapter\_id (all resolve). Canonical thread NAMES for any encoding come from T1\_Threads\_22\_Master\_References, never inferred from content.

§3 Active Populate Registries

Twenty-two T0 registries at active populate scope per T1\_Architecture\_and\_State Tier 0 Registry Architecture section. Each registry carries identity block plus authority owner plus current populate state plus column inventory documenting registry-specific schema. Universal columns per §2 apply across all registries and reference by pointer rather than per-registry restatement. Sixteen registries at §3.1 through §3.16 carry 5M-1 lock scope; five registries at §3.17 through §3.21 carry 5M-2 schema absorption scope per pipeline contract spawn; one registry at §3.22 carries Phase 5M-5 Phase F schema absorption scope per HUM-T1-RCM-V1-COMPLETE May 16 paired creation.

§3.1 T0\_Schema\_Dictionary (self)

Drive ID 1tvUe\_6GYiBnPCeQ3sI4RgGw3jVMeHScWmeyHvWUB-EA at /Humanity/00\_Tier\_0\_Master\_Indices/ Drive path.

Current schema version v1.3 at HUM Pre-Chunk-5A Cleanup Pass Session C Wave 3 lock. Authority owner this document itself; per-registry schema documentation absorbs into the per-section schema lookup canonical layer. Status active populate at Phase 5M-5 Phase F lock with 30 registry sections documented at varied per-registry depth covering identity plus column inventory plus populate state. 22 active populate registries at §3 covering §3.1 through §3.22, 6 scope-locked registries at §4, 2 newly spun registries at §5.

Registry-specific scope. T0\_Schema\_Dictionary documents the canonical schema for all 30 documented T0 registries: 22 active populate at §3, 6 scope-locked at §4, 2 newly spun at §5. §6 retains as historical absorbed-at-5M-2 reference pointing to §3.17 through §3.21 promotions per Option B retirement approach. Per-registry sections in §3 through §6 carry canonical schema lookup; universal conventions in §2 apply across all registries by pointer.

Registry-specific columns. The dictionary itself does not carry row-level data per the document-rather-than-sheet convention. The dictionary is a markdown document at canonical Drive path covering schema authority through prose plus structured dash-bullet enumeration. Schema additions across all 30 registries cascade into this dictionary via per-pipeline-contract §X.6 column-add commitments absorbing into per-registry sections in §3 through §5.

§3.2 T0\_Chapter\_Index

Drive ID per T1\_Architecture\_and\_State Tier 0 Registry Architecture section Drive folder resolution at /Humanity/00\_Tier\_0\_Master\_Indices/T0\_Chapter\_Index sheet.

Current schema version v1.1 at 33-column scope. Authority owner T1\_Story\_Spine for chapter-level main story canonical anchor authority plus T1\_Build\_Pipeline\_Contracts §9 Story Spine Pipeline Contract for per-chapter spine cascade structured field scatter. Status active populate at 79 rows covering Prologue plus Ch 01-77 plus Epilogue.

Required columns:

Universal columns per §2 apply.

§3.3 T0\_Region\_Index

ADDENDUM (living-source, 2026-08-03, the leg-6 EG\_0090 ruling): movement\_modifier is REGION-GRAIN and stays honest-blank where a region spans multiple movement biomes (south\_india: temple cities, a training pit, wet-evergreen ghats in one region) — a region-wide token lands only where one biome genuinely governs traversal (flores\_island jungle\_slow). Zone-grain footing rides the Environment\_Grammar classes (exposure\_hazard and the class's own physical read), and a health-drain column is never used as a movement-column substitute.

Drive path /Humanity/00\_Tier\_0\_Master\_Indices/T0\_Region\_Index sheet.

Current schema version v1.0 at 8-column scope expands to populate scope at Phase 5M. Authority owner T1\_World\_Geography\_Master v2.3 for per-region geographic substrate plus T1\_Region\_Page\_Template v1.0 for region page schema plus T1\_Build\_Pipeline\_Contracts §7 Region Page Build Pipeline Contract for region page build canonical authority. Status active populate at 69 rows covering canonical regions across 77 chapters per multi-chapter region grouping.

Required columns:

Pipeline contract column adds at Phase 5M lock per pipeline contract iteration:

Universal columns per §2 apply.

§3.4 T0\_Thread\_Grid

Drive path /Humanity/00\_Tier\_0\_Master\_Indices/T0\_Thread\_Grid sheet.

Current schema version v1.0 at 22-thread by 79-chapter grid scope. Authority owner T1\_Threads\_22\_Master\_References v2.2 for 22-thread canonical roster plus T1\_Build\_Pipeline\_Contracts §9 Story Spine Pipeline Contract for per-chapter thread anchor progression population. Status active populate at 22 × 79 \= 1738 grid cells with cascade-authored thread anchor progression population scope.

Required columns:

Universal columns per §2 apply.

§3.5 T0\_Vril\_Site\_Registry

Drive path /Humanity/00\_Tier\_0\_Master\_Indices/T0\_Vril\_Site\_Registry sheet.

Current schema version v0.1 at 30-row populate scope. Authority owner T1\_Vril\_and\_Magic\_System\_Master v2.2 for vril site canonical authority including Component 11 9-anchor catalog per CVD §3 reframe history. Status active populate at 30 rows covering canonical vril site roster through Phase 5M-5 Phase F sheet population landing. VS\_CH63\_001 Nan Madol row landed at Phase F per Phase D D-9 secondary finding migration from VS\_CHTBD\_PACIFIC\_001 to chapter-anchored format. Canonical anchor catalog locks at 9 sites per CVD v1.1 §19.1 reframe (Serapeum, Puma Punku, Antikythera, Great Pyramid, Baalbek, Göbekli Tepe, Sacsayhuamán, Nan Madol, Newgrange) with Gunung Padang dropped per March 2024 Natawidjaja retraction.

Drift item resolution from v0.1 patches at prior dictionary locks. Vril\_Site\_Registry engineering\_anomaly\_flag enum patches from 7-anchor list including Gunung Padang to canonical 9-anchor list per CVD v1.1 §19.1 reframe — patch resolved at Phase 5M-5 Phase F sheet population landing with all 9 canonical anchors (Serapeum VS\_CH15\_002, Puma Punku VS\_CH52\_001, Antikythera VS\_CH23\_001, Great Pyramid VS\_CH15\_001, Baalbek VS\_CH18\_001, Göbekli Tepe VS\_CH25\_001, Sacsayhuamán VS\_CH51\_002, Nan Madol VS\_CH63\_001, Newgrange VS\_CH24\_001) reading engineering\_anomaly\_flag=TRUE.

Required columns:

Universal columns per §2 apply.

§3.6 T0\_Inscription\_Spine

Drive path /Humanity/00\_Tier\_0\_Master\_Indices/T0\_Inscription\_Spine sheet.

Current schema version v0.1 at 99-row 15-column scratchpad scope. Authority owner T1\_Languages\_and\_Script\_Master v2.1 for per-chapter inscription beat substrate plus twelve-tier inscription mastery readability per CVD §12.1 framework plus fairy-realm-script arc seeded Ch 8 through Ch 70-77 reveal plus hidden-inscription 77-fragment House of Velheim ancient document spine. Status active populate at 99-row scratchpad expanding to full populate scope at Phase 5M Drive populate.

Required columns:

Universal columns per §2 apply.

§3.7 T0\_Language\_Script\_Registry

Drive path /Humanity/00\_Tier\_0\_Master\_Indices/T0\_Language\_Script\_Registry sheet.

Current schema version v0.1 at 73-row 18-column scratchpad scope. Authority owner T1\_Languages\_and\_Script\_Master v2.1 for canonical authority on language and script content per Phase 5D close. Status active populate at 73-row scratchpad expanding to full populate scope at Phase 5M Drive populate.

Required columns:

Drift item from v0.1 patches at this dictionary lock. Blueprint section 4.1 and Blueprint section 4.3 authority anchors redirect to T1\_Architecture\_and\_State Tier 0 Registry Architecture section per Blueprint v4.1 archive at 5L Distribution.

Pre-existing format honored. Descriptive slug primary key format covers canonical existing slugs; LANG\_NNN universal pattern proposed at §2.7 but not locked at 5M-1 to honor pre-existing canonical identifier load. Per-registry populate session at Phase 5M Drive populate carries the descriptive-slug-versus-LANG\_NNN decision with author confirmation.

Universal columns per §2 apply.

§3.8 T0\_Worldstate\_Variables

Drive path /Humanity/00\_Tier\_0\_Master\_Indices/T0\_Worldstate\_Variables sheet.

Current schema version v1.0 at 25-row scope. Authority owner T1\_Integrity\_Paths\_Worldstates\_Master v2.1 for canonical authority on integrity-path-convergence framework plus Journal mechanic spec plus Five Integrity Three Path framework per CVD §7. Status active populate at 25 rows covering canonical worldstate variables per Five Integrity Three Path framework convergence rule.

Required columns:

Universal columns per §2 apply.

§3.9 T0\_Antagonist\_Network\_Registry

Drive path /Humanity/00\_Tier\_0\_Master\_Indices/T0\_Antagonist\_Network\_Registry sheet.

Current schema version v1.0 at 62-row scope. Authority owner T4\_House\_of\_Velheim\_Canonical v1.0 for antagonist family identity authority plus CVD §17.7 antagonist family identity discipline binding Velheim and Cassius Velheim canonical antagonist family and patriarch names. Status active populate at 62 rows covering canonical antagonist family network operatives and named characters.

Required columns:

Universal columns per §2 apply.

§3.10 T0\_Character\_Index

Drive path /Humanity/00\_Tier\_0\_Master\_Indices/T0\_Character\_Index sheet.

Current schema version v1.0 at 118-row populate scope. Authority owner T3\_Core\_Characters v1.0 and T3\_Supporting\_Characters v1.0 for canonical character substrate plus T1\_Story\_Spine for protagonist arc canonical authority. Status active populate at 118 rows covering canonical NPC roster across the 77-chapter arc.

Drift item resolution from prior populate work. Character primary key format renamed from CH\_NNNN (4-digit zero-pad colliding with chapter CH\_NN canonical format per Buildability Audit P0) to CHAR\_NNNN per §2.7 of this dictionary plus §2.8 cross-registry collision avoidance. 118-row batch rename landed at Phase 5M-5 Phase F sheet population landing covering CHAR\_0001 through CHAR\_0118; cross-registry foreign-key references resolve to the canonical CHAR\_NNNN format across all referring registries.

Required columns:

Universal columns per §2 apply.

§3.11 T0\_Ability\_Tree\_Registry

Drive path /Humanity/00\_Tier\_0\_Master\_Indices/T0\_Ability\_Tree\_Registry sheet.

Current schema version v1.4 at 185-row scope. Authority owner T1\_Ability\_Tree v1.4 for canonical ability framework per Phase 5G close plus twelve-tier Hermetic mastery framework per CVD §12.1. Status active populate at 185 abilities with headroom for Phase 6 region build feedback expansion.

Required columns:

Universal columns per §2 apply.

§3.12 T0\_Hard\_Lines

Drive path /Humanity/00\_Tier\_0\_Master\_Indices/T0\_Hard\_Lines sheet at gdoc ID 14bOfVe per userMemories session 5L target.

Current schema version v1.0 at 120-row TSV sheet scope. Authority owner CVD §17 hard lines canonical authority plus per-T1-refine surfacing as T1 docs lock through Phase 5\. Status active populate at 120 rows covering aggregated hard lines from CVD §17 plus T1 reference doc surfacing.

Required columns:

Universal columns per §2 apply.

§3.13 T0\_Weapon\_Registry

Drive path /Humanity/00\_Tier\_0\_Master\_Indices/T0\_Weapon\_Registry sheet.

Current schema version v0.1 placeholder at Phase 6 target. Authority owner T1\_Combat\_System\_Spec for 72-weapon canonical roster (36 Brute plus 36 Trickery) plus Gate 10 regional combat identity per Pillar 10\. Status pending Phase 6 populate; minimum-viable schema documents at this dictionary for downstream consumer pinning.

Required columns:

Universal columns per §2 apply.

§3.14 T0\_Familiar\_Registry

Drive path /Humanity/00\_Tier\_0\_Master\_Indices/T0\_Familiar\_Registry sheet.

Current schema version v0.1 placeholder at Phase 6 target. Authority owner T1\_Ability\_Tree v1.4 for familiar bond canonical framework plus CVD §17.12 cardinal numerical canon for 33 leg-tier species (21 mortal plus 12 elven) plus 22 player slots (21 base plus 1 path-variable 22nd). Status pending Phase 6 populate; minimum-viable schema documents at this dictionary for downstream consumer pinning.

Required columns:

Universal columns per §2 apply.

§3.15 T0\_Questline\_Index

Drive path /Humanity/00\_Tier\_0\_Master\_Indices/T0\_Questline\_Index sheet.

Current schema version v0.1 placeholder at Phase 6 target. Authority owner T1\_Story\_Spine for Main Story questline canonical authority plus T1\_Trades\_Master for 10 Trade Questline canonical roster plus CVD §11.1 for 12 Side Questline canonical roster (Fairy Tale and Folklore, Military History, Archaeology/Inscription/Occult, Mystery/Detective, Astrology/Psychology, Pirate/Naval, Sorcery/Music Theory, Trickery/Gambling, Cryptids, Anomalous Phenomena, Lost Civilizations, Secret Societies). Status pending Phase 6 populate at 23 rows (Main Story plus 10 Trade plus 12 SQ).

Required columns:

Universal columns per §2 apply.

§3.16 T0\_SFX\_Registry

Drive path /Humanity/00\_Tier\_0\_Master\_Indices/T0\_SFX\_Registry sheet creates at 5M Drive populate per §10 of T1\_Build\_Pipeline\_Contracts.

Current schema version v0.1 at creation per T1\_Build\_Pipeline\_Contracts §10 SFX Pipeline Contract lock. Authority owner T1\_Build\_Pipeline\_Contracts §10 for canonical SFX schema specification plus CVD §6 cultural depiction standard for ritual-context audio at high-care cultural chapter scope. Status active populate at Drive populate creating the registry at 17th New T0 Registry per §10 Decision 1A lock.

Required columns per §10.5 of T1\_Build\_Pipeline\_Contracts:

Universal columns per §2 apply.

§3.17 T0\_Theme\_Registry

Drive path /Humanity/00\_Tier\_0\_Master\_Indices/T0\_Theme\_Registry sheet pending 5M-3 Drive populate.

Current schema version v1.0 at creation per T1\_Build\_Pipeline\_Contracts §3 AIVA Pipeline Contract §3.6 lock. Authority owner T1\_Build\_Pipeline\_Contracts §3 AIVA Pipeline Contract for canonical theme registry schema specification plus CVD §6 cultural depiction standard for cultural\_substrate fields at high-care cultural chapter scope plus CVD §17 hard line authority for hard\_line\_relevance fields. Status active populate at 5M-3 Drive populate creating the registry per Decision 3B as one of 5 spawned-by-pipeline T0 registries absorbing schema at Phase 5M-2.

Entity ID format descriptive snake\_case slug per §2.7 pre-existing pipeline contract canonical spec. Examples PROTAGONIST\_THEME, HOUSE\_OF\_VELHEIM\_THEME, ARCHITECT\_THEME, CASSIUS\_PHASE\_1, CASSIUS\_PHASE\_2, CASSIUS\_PHASE\_3, GRAND\_SAGE\_REVEAL, ENDING\_TRULY\_GOOD, ENDING\_GOOD\_ENOUGH, ENDING\_EVIL, VIMANA\_ACTIVATION, FAMILIAR\_BOND. TH\_NNNN universal pattern proposed migration option deferred to per-registry populate session author confirmation.

Required columns per §3.5 and §3.6 of T1\_Build\_Pipeline\_Contracts plus §5.6 cross-pipeline column add:

Universal columns per §2 apply.

§3.18 T0\_Voice\_Registry

Drive path /Humanity/00\_Tier\_0\_Master\_Indices/T0\_Voice\_Registry sheet pending 5M-3 Drive populate.

Current schema version v1.0 at creation per T1\_Build\_Pipeline\_Contracts §4 ElevenLabs Pipeline Contract §4.6 lock. Authority owner T1\_Build\_Pipeline\_Contracts §4 ElevenLabs Pipeline Contract for canonical voice registry schema specification plus §4.4.1 Voice Clone Authorization gate canonical authority plus CVD §6 cultural depiction standard for cultural\_anchor fields at high-care cultural chapter scope plus CVD §17 hard line authority for hard\_line\_relevance fields. Status active populate at 5M-3 Drive populate creating the registry per Decision 4 as one of 5 spawned-by-pipeline T0 registries absorbing schema at Phase 5M-2.

Entity ID format descriptive snake\_case slug per §2.7 pre-existing pipeline contract canonical spec. Examples PROTAGONIST\_VOICE\_BASE, PROTAGONIST\_VOICE\_AGE\_VARIANT\_CHILDHOOD, GRAND\_SAGE\_REVEAL\_VOICE, ARCHITECT\_VOICE, CASSIUS\_PHASE\_1\_VOICE, CASSIUS\_PHASE\_2\_VOICE, CASSIUS\_PHASE\_3\_VOICE, FAMILY\_OPERATIVE\_EXTRACTIVE\_SECTOR\_ARCHETYPE, NPC\_CH29\_NOAIDI\_NAMED, AMBIENT\_CROWD\_CH12\_YORUBA\_MARKET. VO\_NNNN universal pattern proposed migration option deferred to per-registry populate session author confirmation.

Required columns per §4.5 and §4.6 of T1\_Build\_Pipeline\_Contracts plus §5.6 cross-pipeline column add:

Universal columns per §2 apply.

§3.19 T0\_Scene\_Spec\_Registry

Drive path /Humanity/00\_Tier\_0\_Master\_Indices/T0\_Scene\_Spec\_Registry sheet pending 5M-3 Drive populate.

Current schema version v1.0 at creation per T1\_Build\_Pipeline\_Contracts §5 Cinematic Scene Build Pipeline Contract §5.5 and §5.6 lock. Authority owner T1\_Build\_Pipeline\_Contracts §5 Cinematic Scene Build Pipeline Contract for canonical scene spec registry schema specification plus §5.4.1 director-in-loop discipline canonical authority plus CVD §17 hard line authority for hard\_line\_relevance fields. Status active populate at 5M-3 Drive populate creating the registry per Decision 4A as 14th New T0 Registry, one of 5 spawned-by-pipeline T0 registries absorbing schema at Phase 5M-2.

Entity ID format descriptive snake\_case slug per §2.7 pre-existing pipeline contract canonical spec. Examples SCENE\_CH77\_ENDING\_TRULY\_GOOD, SCENE\_CH77\_ENDING\_GOOD\_ENOUGH, SCENE\_CH77\_ENDING\_EVIL, SCENE\_CH76\_GRAND\_SAGE\_REVEAL, SCENE\_CH76\_CASSIUS\_PHASE\_1\_INTRO, SCENE\_CH76\_CASSIUS\_PHASE\_TRANSITION\_1\_TO\_2, SCENE\_CH76\_CASSIUS\_PHASE\_TRANSITION\_2\_TO\_3, SCENE\_CH74\_CASSIUS\_RESOLUTION\_TRULY\_GOOD, SCENE\_CH55\_VIMANA\_ACTIVATION, SCENE\_CH58\_VIMANA\_ACTIVATION, SCENE\_CH18\_ARCHITECT\_APPEARANCE, SCENE\_PROLOGUE\_OPENING, SCENE\_EPILOGUE\_CLOSING. SC\_NNNN universal pattern proposed migration option deferred to per-registry populate session author confirmation.

Required columns per §5.5 and §5.6 of T1\_Build\_Pipeline\_Contracts plus §6.6 cross-pipeline column add:

Universal columns per §2 apply.

§3.20 T0\_Quest\_Definition\_Registry

Drive path /Humanity/00\_Tier\_0\_Master\_Indices/T0\_Quest\_Definition\_Registry sheet pending 5M-3 Drive populate.

Current schema version v1.0 at creation per T1\_Build\_Pipeline\_Contracts §6 Quest Writing Pipeline Contract §6.5 and §6.6 lock. Authority owner T1\_Build\_Pipeline\_Contracts §6 Quest Writing Pipeline Contract for canonical quest definition registry schema specification plus §6.4.1 author-in-loop discipline canonical authority plus CVD §17 hard line authority for hard\_line\_relevance fields plus CVD §12.1 twelve-tier Hermetic Mastery framework for twelve\_tier\_gate field. Status active populate at 5M-3 Drive populate creating the registry per Decision 4A as 15th New T0 Registry, one of 5 spawned-by-pipeline T0 registries absorbing schema at Phase 5M-2.

Entity ID format descriptive snake\_case slug per §2.7 pre-existing pipeline contract canonical spec. Examples QUEST\_CH77\_ENDING\_TRULY\_GOOD, QUEST\_CH77\_ENDING\_GOOD\_ENOUGH, QUEST\_CH77\_ENDING\_EVIL, QUEST\_CH76\_GRAND\_SAGE\_REVEAL, QUEST\_CH76\_CASSIUS\_PHASE\_1, QUEST\_CH76\_CASSIUS\_PHASE\_TRANSITION\_1\_TO\_2, QUEST\_CH55\_VIMANA\_ACTIVATION, QUEST\_CH18\_ARCHITECT\_APPEARANCE, QUEST\_TRADE\_07\_HAITI\_HOME\_BASE, QUEST\_SQ03\_FAIRY\_REALM\_SCRIPT\_SEALED\_LETTER, QUEST\_WEAPON\_BRUTE\_001\_BOND, QUEST\_FAMILIAR\_22\_FATHER\_REUNION\_TRULY\_GOOD, QUEST\_PROLOGUE\_BASELINE, QUEST\_EPILOGUE\_RESOLUTION\_TRULY\_GOOD. QU\_NNNN universal pattern proposed migration option deferred to per-registry populate session author confirmation.

Required columns per §6.5 and §6.6 of T1\_Build\_Pipeline\_Contracts:

Dialogue dataset file structure referenced by dialogue\_dataset\_array column is build-asset file structure not a T0 registry. Sub-spec per §6.5 covers dialogue\_dataset\_id at DD\_\<character\_id\>\_\<quest\_id\> format, character\_id foreign key to T0\_Character\_Index or T0\_Antagonist\_Network\_Registry, quest\_id foreign key to this registry, dialogue\_node\_array array of dialogue node objects covering node\_id, trigger\_anchor\_id foreign-key to dialogue\_trigger\_anchors on the parent quest, dialogue\_type covering monologue or six\_option\_voice\_response or branch\_decision or scripted\_response, line\_variant\_array per line variant condition coverage, six\_option\_array where dialogue\_type is six\_option\_voice\_response per CVD §13 voice system covering Truly Good Truly Bad Sympathetic Detached Curious Defiant six options, branch\_target\_array where dialogue\_type is branch\_decision pointing to subsequent node\_ids per branch outcome. Per-variant line condition coverage includes integrity\_score range, path\_bucket, biography\_state object referencing T1\_Integrity\_Paths\_Worldstates\_Master worldstate variables, age\_stage, appearance\_score range, relationship\_history with named NPC, default\_variant boolean for the convergence\_neutral fallback case, line\_text containing the actual dialogue text content, per\_line\_direction\_notes object covering emotion\_direction and intensity\_adjustment and elevenlabs\_stability\_override and elevenlabs\_clarity\_override and audio\_tags array for ElevenLabs v3 emotion control schema.

Universal columns per §2 apply.

§3.21 T0\_Source\_Material\_Registry

Drive path /Humanity/00\_Tier\_0\_Master\_Indices/T0\_Source\_Material\_Registry sheet pending 5M-3 Drive populate.

Current schema version v1.0 at creation per T1\_Build\_Pipeline\_Contracts §8 Book Processing Pipeline Contract §8.5 and §8.6 lock. Authority owner T1\_Build\_Pipeline\_Contracts §8 Book Processing Pipeline Contract for canonical source material registry schema specification plus T99\_Project\_2\_Book\_Processing\_Workflow Section 5.1 manifest enrichment workflow plus CVD §6.2 cultural depiction tier framework for cultural\_authenticity\_classification plus CVD §19.1 reframed canonical retraction discipline for canonical\_retraction\_status. Status active populate at 5M-3 Drive populate creating the registry per Decision 4A as 16th New T0 Registry, one of 5 spawned-by-pipeline T0 registries absorbing schema at Phase 5M-2.

Entity ID format SRC\_NNNNN per §2.7 explicit lock conflict-free with §8.5 ordinal format spec. Zero-padded ordinal SRC\_00001 through SRC\_03900-plus across the 2500-plus corpus scope. Stable across registry updates. Used as foreign key from corpus chunk metadata in ChromaDB plus from primary\_source\_array foreign-key columns on canonical content T0 registries.

Required columns per §8.5 and §8.6 of T1\_Build\_Pipeline\_Contracts:

ChromaDB chunk metadata is build-asset regenerable from T0\_Source\_Material\_Registry rows at any time per §8.10 schema version migration discipline. Per-chunk metadata captured at indexing time covers source\_id foreign key, chunk\_index\_in\_source, page\_number, primary\_category, region\_tags, chapter\_scope\_hints, thread\_relevance\_tags, embedding\_vector at 768 dimensions for nomic-embed-text v1.5 or v2-moe. Chunk metadata not a T0 registry row.

Phase 3 category-extraction stream output flows through structured JSON files at /02-Book Processing/category\_extractions/ with naming convention target\_t0\_registry\_stream\_scope.json. Per-stream JSON is build-asset for audit traceability not a T0 registry row. Append-to-canonical-T0-registry workflow per T99\_Project\_2\_Book\_Processing\_Workflow Section 6.3 step 7 reviews extraction output against target registry schema, validates per-entry citations resolve to corpus chunks, appends to canonical T0 sheet on sign-off.

Universal columns per §2 apply.

§3.22 T0\_Research\_Corpus\_Registry

Drive path /Humanity/00\_Tier\_0\_Master\_Indices/T0\_Research\_Corpus\_Registry sheet at gsheet 1JRHTofo3Bqswpb67zSGrPYbVRYr0mubv3G32Q\_Z5WgM.

Current schema version v0.1 at minimum-viable scope. Authority owner T1\_Research\_Corpus\_Master DRAFT v1.1.3b at gdoc 1pxjjONMUFJ54GFfL1FxC6qzr6T1-ImyeZOJCNDiLm-s (currently advanced past v1.0 lock at HUM-T1-RCM-V1-COMPLETE May 16\) for canonical ownership-status convention authority covering USB plus free-PDF source routing through G:\\My Drive\\HUMANITY\\01\_Book\_Research\\A\_Source\_Texts. Status active populate at Phase 5M-5 Phase F lock creating the registry per HUM-T1-RCM-V1-COMPLETE May 16 paired registry creation; per-row data population at Phase 5.6 Corpus Doc Rebuild absorbing Ch 16-77 plus Prologue plus Epilogue against verified T1\_World\_Geography\_Master v2.1 per T1\_Architecture\_and\_State Strategic Roadmap section.

Entity ID format RCE\_NNNNN ordinal proposed at §2.7 with per-registry populate session author confirmation. 5-digit zero-padded ordinal RCE\_00001 through RCE\_NNNNN across the per-chapter corpus entry roster scope. Stable across registry updates. Used as foreign key from T1\_RCM per-chapter H2 section anchors plus from cross-registry corpus references at Phase 6 onward.

Required columns at minimum-viable schema scope:

Cross-reference foreign-key columns linking T0\_Source\_Material\_Registry SRC\_NNNNN to T0\_Research\_Corpus\_Registry RCE\_NNNNN defer to Phase 6 pipeline-driven schema expansion per Phase D D-1 finding pipeline-feed discipline. Phase 5.6 Corpus Doc Rebuild populate authors the per-chapter corpus entry roster against T1\_RCM v1.1 absorption scope.

Universal columns per §2 apply.

§4 Scope-Locked Registries

Six T0 registries at scope-locked state per T1\_Architecture\_and\_State Tier 0 Registry Architecture section. Scope-locked status indicates schema authority is documented at pipeline contract §X.6 column-add commitments plus T1 reference doc authority, with populate deferred to per-registry populate session at Phase 6 or beyond. Per-registry sections in §4 carry minimum-viable schema documentation covering identity plus column-add commitments; full column rosters lock at per-registry populate session.

§4.1 T0\_Boss\_Encounter

Drive path /Humanity/00\_Tier\_0\_Master\_Indices/T0\_Boss\_Encounter sheet pending Phase 6 or earlier creation per Story Spine cascade close.

Current schema version v0.1 placeholder. Authority owner T1\_Combat\_System\_Spec for Gate 8 minimum three-mode blended boss specification plus T4\_House\_of\_Velheim\_Canonical for Cassius Velheim Ch 76 three-phase boss canonical substrate. Status scope-locked; populate at MMO build phase or earlier if main-story bosses surface ahead of MMO scope per Story Spine cascade close.

Entity ID format ENC\_NNN proposed at §2.7 with per-registry populate session author confirmation.

Required columns per §1.6, §2.6, §3.6, §4.6, §5.6, §9.6, §10.6 pipeline contract column-add commitments:

Universal columns per §2 apply.

Realized-schema note (2026-07-24): the live registry at registries/T0\_Boss\_Encounter\_Registry realized this section ahead of the placeholder — BE\_NNNN keys (not ENC\_NNN), 281 rows covering all chapters, 42 columns including win\_condition (controlled verb grammar REDUCE/FREE/PURGE/PACIFY/PERCEIVE/REFUTE/EXPOSE/PART\_BREAK/BYPASS/EVADE), win\_shape, counters, target\_type, restore\_target, ws\_writes, mesh columns. The four columns above are populated for the CH\_02-CH\_05 vertical-slice rows; remaining rows populate per chapter at factory time. Full §4.1 column-list re-alignment to the realized 42-column schema is an open canon-lane item.

Registry-header note — the Hollow encounter vocabulary EXTENSION and the tier-boundary columns (living-source, 2026-07-27). Josh ruled at the ninth sitting that HL\_0080's non-damage protocol is removed for the Hollow class: Hollows are defeated, some encounters run puzzle-forward with real combat inside them and others run action-forward with a per-encounter trick (a damage window, a required combo or parry, environmental-damage-only resolution, and an open palette beyond those), and the full loop is find the cause, enter the rift, and clear both the hollow contamination and the Hollow itself (docs/spine/DECISIONS\_PENDING\_JOSH.md ninth-sitting block JB-1; HOLLOW\_EXPANSION\_INTEGRATION\_2026-07-27 §2.6 and worklist item X-9). The removal is scoped to the Hollow. The row's other subject, the sacred-site atmospheric echo with its six built instances, keeps its non-damage protocol, so no later routing may read this note as un-protecting those set-pieces.

Two controlled-vocabulary values land at this revision as an EXTENSION rather than a population, because neither was live anywhere in the registry layer before it: BLIGHT on ontology\_class and CONTAIN\_BLIGHT on collect\_verb (record §6.2, and §12's positive-control ledger). The live state read 279 empty cells plus 2 CONSTRUCT on ontology\_class and 279 empty cells plus 2 FIGHT on collect\_verb in this registry, with T0\_Creature\_Roster carrying 19 ORDINARY\_FAUNA and 1 DOCUMENT against the same column names; a fixed-string search for CONTAIN\_BLIGHT across the whole registry layer returned zero while the same search matched CONSTRUCT, FIGHT and ORDINARY\_FAUNA, which is the control proving the search could match. The mint is scoped to the encounter surface: T0\_Creature\_Roster keeps its refusal of a CR\_ row for the class, and that absence is the firewall made structural (record §4.9).

The Hollow encounter cell shape, declared here so a later author fills a row rather than deriving one (record worklist X-9): ontology\_class BLIGHT; collect\_verb CONTAIN\_BLIGHT; has\_nonkill\_path TRUE, because the fork is the class's canonical non-kill resolution; defeat\_protected FALSE, because no story progression is gated on a Hollow surviving; win\_condition carrying PERCEIVE followed by the fork terms CLEANSE and ABSORB, which are Josh's own words for the fork the prior grammar recorded as purify and harvest, both now retired synonyms (record §3.1); win\_shape fork; restore\_target naming the place or the person the resolution sets right; and ws\_writes carrying the meter key, the integrity key and the fork key in this registry's ws-prefixed form, covering world\_cleansing\_meter and rift\_node\_state for the ledger, integrity\_score for the cost, WS\_039 hollow\_containment\_fork\_last for the fork memory, and hollow\_absorb\_depth on the absorb branch. The four anti-kill-loot teeth bind every such row (record §3.4): the Hollow's own row never carries a drop anchor, a loot-table reference, or a win\_reward holding an item id, because there is no corpse to loot; rewards attach to the container, never the entity; progression flows through the ledger and the quest rather than a defeat counter, so a Hollows-defeated statistic is a banned surface; and the fork is unskippable, with no auto-resolve and no default on timeout.

Cell-shape sequencing, stated so no row lands ahead of its gate law. The boss-axes gate holds the ruled win\_condition verb enum and the ruled win\_shape set as machine law, and neither CLEANSE, ABSORB nor fork sits in those sets at this revision, so an authored Hollow encounter row carrying the shape above fails that gate until the gate law absorbs the three tokens. The three columns above also extend a stub-superseded registry, so the fidelity baseline's pinned candidate header and the column-ownership manifest both absorb them in the landing commit. Three of the worldstate keys the shape cites are likewise not live yet — world\_cleansing\_meter, rift\_node\_state and hollow\_absorb\_depth all return zero across the registry layer at this revision, while integrity\_score and WS\_039 hollow\_containment\_fork\_last do resolve — so those three land with the worldstate mint and the first Hollow encounter row follows that mint as well. Those steps are director-owned; this revision declares the vocabulary and lands the columns, and the first Hollow encounter row follows all three prerequisites.

Whisper-tier manifestations carry no encounter row at all. The procedural surface is a small set of encounter templates plus a runtime generator rather than a per-instance row (record §5), and no whisper record may appear in any gate reference, any unlock condition, or any completion denominator (record §1.7).

§4.2 T0\_School\_Registry

Drive path /Humanity/00\_Tier\_0\_Master\_Indices/T0\_School\_Registry sheet pending Phase 6 creation.

Current schema version v0.1 placeholder. Authority owner CVD Pillar 4 Occult Mystery Schools framework canonical authority covering Egyptian temple mysteries Ch 15, Mesopotamian scribal Ch 17, Levantine Kabbalistic Ch 18, Chinese Taoist alchemy Ch 21, Greek Eleusinian Ch 23, Druidic Ch 24, Hermetic Ch 27, Sámi shamanic Ch 29, Mesoamerican initiatory Ch 47, Hyperborean and Thule and Lemurian and Agartha Ch 66-69 anchor regions per Drive folder canon. Status scope-locked; populate at Phase 6 region page build feedback.

Entity ID format SCH\_NNN proposed at §2.7 with per-registry populate session author confirmation.

Required columns per §6.6, §7.6, §8.6 pipeline contract column-add commitments:

Universal columns per §2 apply.

§4.3 T0\_Cross\_Cultural\_Link\_Graph

Drive path /Humanity/00\_Tier\_0\_Master\_Indices/T0\_Cross\_Cultural\_Link\_Graph sheet pending Phase 6 creation.

Current schema version v0.1 placeholder. Authority owner CVD §3 Component 3 cultural convergence canon plus CVD Pillar 5 Cross-Cultural Linking framework plus T1\_Threads\_22\_Master\_References v2.2 for thread anchor cross-reference at canonical 22-thread substrate. Status scope-locked; populate at Phase 6 region page build feedback through Section 15 Cross-Regional Connections authoring.

Entity ID format LINK\_NNNN proposed at §2.7 with per-registry populate session author confirmation.

Required columns per §6.6, §7.6, §8.6 pipeline contract column-add commitments:

Universal columns per §2 apply.

Registry-header note — link\_type controlled vocabulary (living-source, 2026-07-08). The populated DRAFT registry (registries/T0\_Cross\_Cultural\_Link\_Graph \[DRAFT v0.1\]/Sheet1.csv) realizes the link-classification role as the column link\_type (the motif\_type placeholder above matured to link\_type at populate, alongside richer populate-time columns including link\_name, source/target anchor + region + chapter, link\_strength, reward\_class, integrity\_visibility, lore\_pointer, evidence\_tier, and primary\_source). This note documents the live column's controlled vocabulary only; it applies no column rename to the frozen T0 xlsx baseline, so the fidelity gate is unaffected. link\_type names the cross-cultural MECHANISM an edge encodes and is what the discovery engine rewards on. The classes populated to date are all mythological / ritual-motif and living-tradition classes: parallel-independent, living-tradition-continuity, diaspora-transmission, reception-transmission, linguistic-cognate, pattern-parallel, contrast-inversion, motif-recurrence, callback, continuity, complement, precedence, sets-up, catalog-membership, catalog-convergence, weaving-progression.

New class at this revision — knowledge-transmission (Foundation Enhancement P0 systemic fix, 2026-07-08). A documented civilizational-KNOWLEDGE transmission chain: a real, primary-source-attested passage of science, mathematics, law, technology, scholarship, or statecraft from one culture to another — for example, Indian decimal place-value numerals to the Baghdad House of Wisdom to Córdoba/Toledo translation movements to the European Renaissance; or Chinese papermaking to Talas (751 CE) to Samarkand to Baghdad to Europe. It is a first-class link\_type that rewards IDENTICALLY to the mythological classes above, so the Pillar-5 cross-cultural discovery engine credits cultures as builders-of-knowledge, not only as bearers-of-myth. It is the link-graph half of the achievement instrumentation whose spine-entry half is the civilizational\_marks field (T1\_Build\_Pipeline\_Contracts §9.5); together they let the locked 22-thread count (CVD §17.11) stay untouched while the achievement dimension is still rewarded. GUARDRAIL: a knowledge-transmission edge is attested diffusion of documented achievement and MUST credit each culture's own agency and invention — it is NEVER a hyperdiffusion / single-superior-source-taught-the-world framing and NEVER fringe pseudo-archaeology (CVD §19 Frame-A; see FOUNDATION\_ENHANCEMENT\_ROADMAP.md P0 thesis-discipline item). No rows are populated at this revision — knowledge-transmission population is Phase-2 weaving, and adding rows or a dedicated column then is a deliberate baseline re-emit, not part of this schema-vocabulary documentation.

Reward-class ratification note (living-source, 2026-07-28 sixteenth sitting). The reward\_class column's assignment rule is RATIFIED and APPLIED: Josh ratified the class table at docs/proposals/REWARD\_TAXONOMY\_TABLE\_2026-07-28.md ("yes ratify and amend", verbatim in docs/spine/DECISIONS\_PENDING\_JOSH.md), closing the CCLG\_REWARD\_TAXONOMY dossier key's await\_josh\_confirm disposition. The enum is the six Josh-authored classes of BATCH1\_RULINGS §9 (LORE, WEAPON\_ABILITY, SCHOOL\_TECHNIQUE, INTUITION\_TIER, PUZZLE\_UNLOCK, DISCOVERY\_UNLOCK); every one of the 184 rows now carries a class (the 62 pre-ratification assignments untouched, the 122 blanks filled by the ratified link\_type-keyed rule with three ratified row-level overrides); evidence\_tier is fully populated (primary where primary\_source attests, else needs\_research — the L197 attestation program for the needs\_research rows rides the book pipeline). The lore\_pointer column carries the LORE-never-empty obligation in TWO declared value shapes: the authored player-facing prose form (the 62 pre-ratification cells) and the machine-derived STRUCTURAL form (a bare LINK\_NNNN id naming the unique chain successor — scaffolding the cascade's per-chapter authoring replaces with real prose, never itself a player-facing string). Compliance accounting lives in docs/pipeline\_review/REWARD\_TAXONOMY\_EXCEPTION\_LIST\_2026-07-28.md (74 of 74 fills noncompliant until the cascade authors onward payoffs), never silent. Live-roster completion for this note (the spec-vs-CSV agreement clause): the populate-time columns also include evidence\_basis (the citation text the evidence\_tier labels), component\_anchor (CVD §3 Component 3, the authority owner), populated\_from (row provenance), and extensions (the declared extension-zone tail).

§4.4 T0\_Creature\_Roster

Drive path /Humanity/00\_Tier\_0\_Master\_Indices/T0\_Creature\_Roster sheet pending Phase 6 creation; absorbed Folklore\_Entity\_Registry function in Phase 5M-prep triage per userMemories.

Current schema version v0.1 placeholder. Authority owner T1\_World\_Geography\_Master v2.3 for biome substrate plus T1\_Combat\_System\_Spec for predator-prey ecology canonical authority within regional combat identity per Pillar 10 plus T1\_Integrity\_Paths\_Worldstates\_Master for Pillar 12 Layer 3 integrity-visible aesthetic shift on fauna behavior. Status scope-locked; populate at Phase 6 region page build feedback.

Entity ID format CR\_NNNN proposed at §2.7 with per-registry populate session author confirmation.

Required columns per §2.6, §6.6, §7.6, §8.6 pipeline contract column-add commitments:

Universal columns per §2 apply.

ADDENDUM (living-source, 2026-08-03, with the Ch-2 corrections pass): the column list above is a v0.1 placeholder that lags the live 57-column header (150 rows) — the full §4.4 refresh against that header is a BOOKED obligation on the RANK-0 queue. Ratified here so the vocabulary has a canon-layer home (it previously lived only in the proposal-tier WS7 wiring plan): the collectibility-ontology trio declared in docs/registry\_extensions.json takes ontology\_class ∈ LEGENDARY | ORDINARY\_FAUNA | SACRED | CONDEMNED | AMBIVALENT | CONSTRUCT | BLIGHT; collect\_verb ∈ BOND | TAME\_BREED | DOCUMENT | FREE\_ALLY | FIGHT | CONTAIN\_PURGE | EARN | CONTAIN\_BLIGHT; dex\_completion\_class ∈ SPECIES | VARIANT | OBSERVATION\_CHAIN | WITNESS | CONTAINMENT | NA. The enums grow by ratified values under critic gate, never by free text. TAME\_BREED carries the TAME arm only — a breeding claim lives on husbandry\_breedable, never in the verb. trophic\_role additionally admits the ratified token vital-force predator (2026-08-03, the polo row; the project's own phrase per CH\_02 Thread 3 / LINK\_0152). combat\_permission (declared extension column, 2026-08-03, the D4 ruling with the leg-2b critic's not-person family folded in): TARGETABILITY ONLY, single-valued, populated only where canon rules and BLANK where canon is silent — NONE | PERMITTED | PROTECTED | FOLKLORE\_FACED | CONSTRUCT\_NOT\_PERSON | MANIFESTATION\_NOT\_PERSON | ENVIRONMENTAL\_NOT\_PERSON. The encounter layer owns per-chapter staging (the reticulated python is PERMITTED as the Ch-2 guardian test while the Ch-3 naga tana staging on the same row is appeased-not-slain — the row token never overrides the spine's encounter ruling).

§4.5 T0\_Quest\_Seed\_Registry

CORRECTED IN PLACE (living-source, 2026-08-02, with the registry's first four rows — SEED\_0001..SEED\_0004): this section previously declared a 12-column Drive-era placeholder schema (seed\_id/seed\_type/premise/npc\_anchor/...) and an authority owner of T1\_Vril\_and\_Magic\_System\_Master. The FROZEN xlsx and the live CSV both carry a different 21-column quest-shaped header, so the placeholder column list was stale against the registry's own reference sheet and is retired here. Only the entity ID family survived the divergence and it stands.

Authority owner: T1\_Build\_Pipeline\_Contracts §6.5 (Quest Spec Schema) — it names this registry as a CG-01 population target, pins the inbound reward\_seed\_refs FK, owns the quest\_type vocabulary the quest\_class column takes, and carries the 2026-08-02 director column note (quest\_class = a §6.5 quest\_type member or the explicit literal none; track\_classification = the CVD §18.2 engagement tracks; tier\_classification RESERVED-BLANK until ruled; quest\_name = working labels pinned FString at codegen).

Entity ID format SEED\_NNNN per §2.7, confirmed at the 2026-08-02 populate session (note: the live header's primary-key COLUMN is named quest\_id; it carries SEED\_NNNN values by design).

Live columns (the frozen 21-column header, verbatim): quest\_id, quest\_name, quest\_class, track\_classification, chapter\_anchor, region\_id, tier\_classification, quest\_thread\_anchor, sq\_anchor, trade\_anchor, prerequisite\_quest\_ids, integrity\_band\_branching, canonical\_outcomes, hard\_line\_anchors, cultural\_depiction\_required, vril\_mechanic\_anchor, rng\_drop\_anchor, pipeline\_consumer, populated\_from, notes, extensions.

TWO SEED FAMILIES, ruled at first population: the SPINE SQ\*\_SEED / reward-map anchors (canon-tier, authorised by a chapter's [POPULATE→T0\_Quest\_Seed\_Registry] tag) land here; the EXR book-extraction seeds (proposal-tier, docs/proposals/quest\_seed\_queue/, tracked by the QUEST\_SEED\_HOUSING\_LEDGER and gate seed\_housing) do NOT enter this registry by extraction — routing one requires the §7.5 typing step plus a same-commit ledger re-disposition. The two families share no id space.

ADDENDUM (living-source, 2026-08-03, WQ_0023 director-first ruling): rng\_drop\_anchor is a declared FK — a semicolon-joined list of T0\_RNG\_Drop\_Table drop\_id values, no spaces (the roster/drop array separator convention; a seed can anchor several drop payloads, the Ch-7 SQ3 marma map + rasayana lore being the shape that forced the ruling). Blank is a legal declared state meaning no drop-lane payload joins the seed. The cell is populated by the deterministic back-join sweep each time a chapter's drop lane lands, with the mapping derived from the drop rows' own populated\_from/notes citations, never invented; the fk\_spec entry landed with this ruling.

§4.6 T0\_RNG\_Drop\_Table

Drive path /Humanity/00\_Tier\_0\_Master\_Indices/T0\_RNG\_Drop\_Table sheet pending Phase 5M column lock per §1.6 of T1\_Build\_Pipeline\_Contracts.

Current schema version v0.1 placeholder. Authority owner T1\_RNG\_Sigma\_Constraint\_System for sigma-bounded RNG floor and ceiling canonical mechanic per CVD §17.13. Status scope-locked; column lock at Phase 5M per §1.6 column-add commitments.

Entity ID format DROP\_NNNNN proposed at §2.7 with per-registry populate session author confirmation.

Required columns per §1.6 of T1\_Build\_Pipeline\_Contracts:

Universal columns per §2 apply.

§5 Newly Spun Registries

Two T0 registries spawned through Phase 5 cascade work per T1\_Architecture\_and\_State Tier 0 Registry Architecture section. Newly spun status indicates registry creates outside the original Blueprint v4.1 §4 spec roster; canonical authority lock at this dictionary plus per-registry T1 reference doc authority.

§5.1 T0\_Trade\_Registry

Drive path /Humanity/00\_Tier\_0\_Master\_Indices/T0\_Trade\_Registry sheet at gdoc ID 1WZjjs2am per userMemories session 5I close.

Current schema version v1.0 at 10-row 8-column scope. Authority owner T1\_Trades\_Master v1.0 for canonical authority on 10 trades per CVD §11.1 plus twelve-tier mastery progression per CVD §12.1. Status active populate at 10 rows covering Animal Communication, Mining, Blacksmithing, Herbalism, Alchemy, Tailoring, Culinary Arts, Engineering, Inscription, Fishing and Navigation.

Required columns:

Universal columns per §2 apply.

§5.2 T0\_Thread\_Registry

Drive path /Humanity/00\_Tier\_0\_Master\_Indices/T0\_Thread\_Registry sheet pending Phase 5M Drive populate.

Current schema version v0.1 placeholder. Authority owner T1\_Threads\_22\_Master\_References v2.2 for canonical authority on 22-thread architecture per Phase 5B close. Status newly spun; populate at Phase 5M Drive populate or later session per Phase 5 plan sequencing.

T0\_Thread\_Registry holds canonical 22-thread roster at registry level distinct from T0\_Thread\_Grid which holds 22-thread by 79-chapter grid cells. Registry carries per-thread canonical authority substrate; Grid carries per-chapter-per-thread progression cells.

Required columns:

Universal columns per §2 apply.

§6 Pending 5M-2 Registries Absorbed

Five T0 registries spawned through pipeline contract iteration absorb at this dictionary v1.1 lock per T99\_Phase\_5\_Closing\_Sequence\_Handoff §5.2 split. Each registry promoted to §3 active populate section per pipeline contract §X.5 and §X.6 full schema absorption. Cascade history retained at this section for forensic provenance.

## §7 Version History

v1.0 ACTIVE lock at Phase 5M-1 close. Initial T0\_Schema\_Dictionary canonical lock covering universal conventions plus per-registry schema documentation for 24 in-scope T0 registries plus forward references for 5 pending 5M-2 spawned registries. Decisions locked per Phase 5M-1 session: per-registry doc structure with universal-conventions intro at §2, populated\_from format at JSON object mapping field-name to source array at §2.2, per-registry MAJOR.MINOR.PATCH schema version semantics at §2.3, universal entity\_id roster at §2.7 covering 15 locked-at-5M-1-scope prefixes plus 5 locked-at-5M-2-scope prefixes plus 6 proposed-at-per-registry-populate-time prefixes, character primary key rename from CH\_NNNN to CHAR\_NNNN per Drift 4 resolution at §2.7 plus §2.8 cross-registry collision avoidance, 5M-1 plus 5M-2 split per T99\_Phase\_5\_Closing\_Sequence\_Handoff §5.2 default.

Drift items absorbed at v1.0 lock. T0\_Vril\_Site\_Registry engineering\_anomaly\_flag canonical anchor catalog patches from CVD v1.0 7-anchor list including Gunung Padang to CVD v1.1 §19.1 reframed 9-anchor list with Gunung Padang dropped per March 2024 Natawidjaja retraction at §3.5. T0\_Schema\_Dictionary v0.1 Blueprint section 4.1 and Blueprint section 4.3 authority anchor references redirect to T1\_Architecture\_and\_State Tier 0 Registry Architecture section per Blueprint v4.1 archive at 5L Distribution at §3.7. T1\_Architecture\_and\_State intro line "Twenty-one Google Sheets registries" stale vs 24 in subsequent lists patches at 5M-5 closing audit T1\_AaS sync pass. T0\_SFX\_Registry overlap accounting between T1\_AaS active populate listing \#16 and T99\_Phase\_5\_Closing\_Sequence\_Handoff §5.2 "six new T0 registry schemas" resolves to T0\_SFX\_Registry documenting at 5M-1 §3.16 alongside other active-populate registries with 5M-2 scope reducing to 5 truly new registries at §6.

Pending at v1.0 lock. Per-registry populate sessions at Phase 6 onward absorb full column rosters for scope-locked registries at §4 plus newly spun T0\_Thread\_Registry at §5.2 plus 5M-2 pending registries at §6. Per-registry primary key format proposed at §2.7 for §4 registries (ENC\_NNN, SCH\_NNN, LINK\_NNNN, CR\_NNNN, SEED\_NNNN, DROP\_NNNNN) locks at per-registry populate session author confirmation. T0\_Language\_Script\_Registry descriptive-slug-versus-LANG\_NNN universal pattern decision defers to per-registry populate session per §3.7. T0\_Vril\_Site\_Registry VS\_CHXX\_NNN composite-id format honors pre-existing canonical lock at §3.5; rename to VS\_NNN with separate chapter\_anchor FK column proposal defers to per-registry populate session author decision.

v1.1 ACTIVE lock at Phase 5M-2 close. MINOR version bump v1.0 → v1.1 absorbing 5 spawned-by-pipeline T0 registry schema documentation from §6 forward references to §3 active populate sections §3.17 through §3.21 per pipeline contract §X.5 and §X.6 full schema absorption. Active populate scope expands from 16 registries at 5M-1 lock to 21 registries at 5M-2 lock; total documented registries holds at 29 across §3 active populate (21), §4 scope-locked (6), §5 newly spun (2). §6 retains as historical absorbed-at-5M-2 note pointing to §3.17 through §3.21 promotions for forensic provenance per Option B retirement approach.

Decisions locked per Phase 5M-2 session. §2.7 framing patch resolves Ambiguity 1 entity\_id format conflict between Schema Dictionary §2.7 v1.0 PREFIX\_NNNN universal pattern lock and Pipeline Contracts §3.6, §4.6, §5.5, §6.5 descriptive snake\_case slug canonical-spawn spec for TH/VO/SC/QU registries. Path C hybrid framing patch at §2.7 only honors descriptive-slug format as canonical pre-existing per pipeline contract spawn parallel to T0\_Vril\_Site\_Registry VS\_CHXX\_NNN composite-id treatment at §3.5 and T0\_Language\_Script\_Registry descriptive slug treatment at §2.7 bottom note. TH\_NNNN, VO\_NNNN, SC\_NNNN, QU\_NNNN universal patterns retain as proposed migration deferred to per-registry populate session author confirmation. Pipeline contract §3.6, §4.6, §5.5, §6.5 retain unchanged at v0.2 lock. T0\_Source\_Material\_Registry SRC\_NNNNN format conflict-free at §2.7 explicit lock matching §8.5 ordinal format spec.

Drift items absorbed at v1.1 lock. None beyond Ambiguity 1 resolution above; no canonical conflict surfaces during 5M-2 schema absorption pass.

Pending at v1.1 lock. T0\_Theme\_Registry, T0\_Voice\_Registry, T0\_Scene\_Spec\_Registry, T0\_Quest\_Definition\_Registry, T0\_Source\_Material\_Registry Drive populate creates registry sheets at 5M-3 Drive populate per T99\_Phase\_5\_Closing\_Sequence\_Handoff §5.3. Per-row data population at 5M-3 and beyond per pipeline contract orchestration discipline. Per-registry primary key format decision (descriptive snake\_case slug versus PREFIX\_NNNN) deferred to per-registry populate session author confirmation for the 4 conflict-affected registries. T0\_Source\_Material\_Registry primary key locks at SRC\_NNNNN ordinal at 5M-3 Drive populate without deferred decision.

v1.2 ACTIVE lock at Phase 5M-5 Phase F close. MINOR version bump v1.1 → v1.2 absorbing T0\_Research\_Corpus\_Registry schema documentation at new §3.22 active populate section per HUM-T1-RCM-V1-COMPLETE May 16 paired registry creation. Active populate scope expands from 21 registries at 5M-2 lock to 22 registries at Phase 5M-5 Phase F lock; total documented registries advances from 29 at 5M-2 lock to 30 at Phase F lock across §3 active populate (22), §4 scope-locked (6), §5 newly spun (2).

PATCH-grade drift fixes absorbed at v1.2 lock alongside MINOR-grade §3.22 addition. Drive path drift corrected across §3.1 through §3.21, §4.1 through §4.6, §5.1 through §5.2: canonical Tier 0 folder path /Humanity/00\_Tier\_0\_Master\_Indices/ at folder ID 1ni2qIY44X47qZ26fxPCU7lF2RL6AEJPZ replaces stale /Humanity/08-Canonical Reference/Tier\_0/ path per T1\_Architecture\_and\_State v3.0 Drive Folder Structure section. §3.5 T0\_Vril\_Site\_Registry state update: 30 rows populated reflecting Phase 5M-5 Phase F VS\_CH63\_001 Nan Madol migration per Phase D D-9 secondary finding (chapter-anchored format replaces prior VS\_CHTBD\_PACIFIC\_001 placeholder); engineering\_anomaly\_flag canonical 9-anchor catalog locked across all 9 anchor rows. §3.10 T0\_Character\_Index state update: CH\_NNNN to CHAR\_NNNN rename resolved at Phase 5M-5 Phase F sheet population landing covering CHAR\_0001 through CHAR\_0118 per Phase D D-7 finding. §2.7 universal entity\_id roster CHAR\_NNNN entry state update parallels §3.10 resolution.

Decisions locked per Phase 5M-5 Phase F session. T0\_Research\_Corpus\_Registry entry\_id format proposed at RCE\_NNNNN ordinal at §2.7 with per-registry populate session author confirmation deferred to Phase 5.6 Corpus Doc Rebuild parallel to scope-locked §4 registry treatment. Minimum-viable schema lock at §3.22 covers chapter foreign-key plus entry\_type plus ownership\_status plus cultural authenticity plus routing-source-substrate plus T1\_RCM section anchor; cross-reference foreign-key column expansions linking T0\_Source\_Material\_Registry to T0\_Research\_Corpus\_Registry defer to Phase 6 pipeline-driven schema expansion per Phase D D-1 finding pipeline-feed discipline.

Drift items absorbed at v1.2 lock. Four PATCH-grade drift fixes per the patch set above; no canonical conflict surfaces during §3.22 schema absorption pass.

Pending at v1.2 lock. T0\_Research\_Corpus\_Registry Drive populate creates row data at Phase 5.6 Corpus Doc Rebuild absorbing Ch 16-77 plus Prologue plus Epilogue against verified T1\_World\_Geography\_Master v2.1 per T1\_Architecture\_and\_State Strategic Roadmap section. Per-row data population at Phase 5.6 onward. RCE\_NNNNN entry\_id format final confirmation locks at Phase 5.6 per-registry populate session author confirmation. T0\_Research\_Corpus\_Registry to T0\_Source\_Material\_Registry cross-reference foreign-key column expansions surface at Phase 6 pipeline-driven schema expansion per Phase D D-1 finding pipeline-feed discipline.

v1.3 ACTIVE lock at HUM Pre-Chunk-5A Cleanup Pass Session C Wave 3\. MINOR version bump v1.2 → v1.3 absorbing canonical authority for extensions column convention at new §2.9 universal conventions subsection per Decision Blueprint §4.1 redirect Option B selection, plus T1 reference doc version-citation refresh across 12 per-registry authority owner citations reflecting Wave 2c addendum canonical state.

§2.9 extensions column convention absorbs canonical authority for extensions column forward-compatibility JSON storage previously residing at Blueprint v4.1 §4.1. Blueprint v4.1 archived at 5L Distribution per T1\_Architecture\_and\_State Tier 0 Registry Architecture section. Five per-registry references at §3.17 through §3.21 patched from Blueprint §4.1 reference to canonical Schema Dictionary §2.9 subsection reference. Decision Option B selected over Option A T1\_AaS redirect per §3.7 precedent and Option C per-pipeline §X.5 redirect per spawning pipeline for canonical single-source-of-truth discipline plus universal-spec scope across §3.17-§3.21 spawned registries.

Drift items absorbed at v1.3 lock. Twelve T1 reference doc version citations advanced reflecting Wave 2c addendum canonical state: T1\_World\_Geography\_Master v2.0 → v2.3 at §3.3 T0\_Region\_Index and §4.4 T0\_Creature\_Roster authority owner citations; T1\_Threads\_22\_Master\_References v2.0 → v2.2 at §3.4 T0\_Thread\_Grid, §4.3 T0\_Cross\_Cultural\_Link\_Graph, and §5.2 T0\_Thread\_Registry authority owner citations; T1\_Vril\_and\_Magic\_System\_Master v2.0 → v2.2 at §3.5 T0\_Vril\_Site\_Registry authority owner citation; T1\_Languages\_and\_Script\_Master v2.0 → v2.1 at §3.6 T0\_Inscription\_Spine and §3.7 T0\_Language\_Script\_Registry authority owner citations; T1\_Integrity\_Paths\_Worldstates\_Master v2.0 → v2.1 at §3.8 T0\_Worldstate\_Variables authority owner citation; T1\_Ability\_Tree v1.1.1+ → v1.4 at §3.11 T0\_Ability\_Tree\_Registry and §3.14 T0\_Familiar\_Registry authority owner citations; T1\_Research\_Corpus\_Master DRAFT v1.1.3a → DRAFT v1.1.3b at §3.22 T0\_Research\_Corpus\_Registry authority owner citation reflecting current Phase 5.6 sub-version per v5-Operational CI active phase declaration.

Decisions locked per Session C Wave 3\. Blueprint §4.1 redirect target lands at Option B absorption into Schema Dictionary §2 Universal Conventions as new §2.9 subsection. Selection rationale covers canonical single-source-of-truth discipline keeping schema-spec authority within the Schema Dictionary, universal scope alignment with the five §3.17-§3.21 spawned registries that share the extensions column convention, and continuity with §2.4 through §2.8 existing universal conventions subsections.

Drift items absorbed at v1.3 lock. None beyond Blueprint redirect resolution above; no canonical conflict surfaces during Wave 3 patch pass.

Pending at v1.3 lock. T0\_Research\_Corpus\_Registry schema expansion to absorb pipeline-feed cross-reference foreign-key columns linking T0\_Source\_Material\_Registry SRC\_NNNNN to T0\_Research\_Corpus\_Registry RCE\_NNNNN defers to Phase 5.6 chunk 5 close per Phase D D-1 finding pipeline-feed discipline per Wave 3 schema audit. T1\_RCM v1.1 ACTIVE lock at Phase 5.6 chunk 5 close triggers paired §3.22 schema expansion per pipeline-driven discipline.

Generated by harness/site/structure_site.py — the URL path is the repo path. review root